${{ github.ref_name }} doesn't work for PRs. We need to change that to ${{ github.head_ref }}, I think.

${{ github.ref_name }} doesn't work for PRs. We need to change that to ${{ github.head_ref }}, I think.

Thanks! Just compared to other workflows. Removing ref altogether should also fix it. It defaults to the event ref/SHA, i.e. the used branch.

${{ github.ref_name }} doesn't work for PRs. We need to change that to ${{ github.head_ref }}, I think.

Thanks! Just compared to other workflows. Removing ref altogether should also fix it. It defaults to the event ref/SHA, i.e. the used branch.

It won't be able to commit the report into the PR branch if relying on the default SHA (which typically is a merge of pr head and base branches.

It won't be able to commit the report into the PR branch if relying on the default SHA (which typically is a merge of pr head and base branches.

Thanks! Should have listened. It indeed can't operate on the default.

Yes, it only updated the timestamp. Let's see how this behave on branches without TPIP updates.
Was briefly concerned about TPIP and CI running in parallel. But that only affects the VSIX packages attached to the branch actions. I.e. all should come together properly on main.
Can probably add a dependency in a later step, was mainly after fixing post-commit action failures.

Having written that, something seems to confuse now the other workflows. Presumably the TPIP commit while the other workflows were running. Need to have another look in the afternoon.

After discussing again with Jonatan, I looks like this is a limitation we have to live with for now. We can review after Embedded World how to further smoothen this process. The only downside is that we worst case have to fiddle around with PRs that change dependencies.